<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>79. Scenario</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="SCENARIO">SCENARIO</h1>
		<h3 id="DEFINITION">DEFINITION</h3>
		<p>Scenarios describe dynamic, time-related interactions between elements: Operational Entities and Actors, the System itself, the System Components. These interactions are expressed through temporally ordered Sequence Messages.</p>
		<p>Scenarios illustrate Capabilities. For example, they are useful to describe</p>
		<ul>
			<li>How Operational Entities and Actors cooperate, and how Operational 	Processes are chained</li>
			<li>How the System is used under operational conditions, how it 	interacts with external Systems and Users</li>
			<li>Use Cases of the system</li>
			<li>Dynamic behavior of the system (either expected or designed): 	dynamicity, order, Modes &amp; States evolutions. etc.</li>
			<li>Non functional constraints or situations: performance expectations 	(latency...), safety failure scenarios, security attacks...</li>
		</ul>
		<h3 id="ICONS">ICONS</h3>
		<p>
			<img height="60" width="75" border="0" src="Images/79.%20Scenario_html_c2a9337.png"/>
		</p>
		<p>
			<br/>
		</p>
	</body>
</html>